Skip to content

fix(deps): update dependency react-error-boundary to v6#120

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/react-error-boundary-6.x
Open

fix(deps): update dependency react-error-boundary to v6#120
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/react-error-boundary-6.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Mar 30, 2026

This PR contains the following updates:

Package Change Age Confidence
react-error-boundary (source) ^4.1.2 → ^6.0.0 age confidence

Release Notes

bvaughn/react-error-boundary (react-error-boundary)

v6.1.1

Compare Source

v6.1.0

Compare Source

  • #​235: Fix error type (Error -> unknown)
  • Export getErrorMessage helper method

v6.0.3

Compare Source

  • Removed react-dom from peer dependencies list; it was accidentally added during a previous internal refactor

v6.0.2

Compare Source

Updated README and generated TS docs

v6.0.1

Compare Source

v6.0.0

Compare Source

Module is ESM-only in order to better work with modern tooling.

v5.0.0

Compare Source

Update withErrorBoundary types to be compatible with the latest forwardRef types

For more background see PR #​211

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) in timezone America/New_York, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Mar 30, 2026 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @openedx/[email protected]
npm error Found: [email protected]
npm error node_modules/react-error-boundary
npm error   react-error-boundary@"^6.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react-error-boundary@"^4.0.11" from @openedx/[email protected]
npm error node_modules/@openedx/frontend-plugin-framework
npm error   @openedx/frontend-plugin-framework@"^1.7.0" from the root project
npm error   @openedx/frontend-plugin-framework@"^1.7.0" from @edx/[email protected]
npm error   node_modules/@edx/frontend-component-header
npm error     @edx/frontend-component-header@"^8.0.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/react-error-boundary
npm error   peer react-error-boundary@"^4.0.11" from @openedx/[email protected]
npm error   node_modules/@openedx/frontend-plugin-framework
npm error     @openedx/frontend-plugin-framework@"^1.7.0" from the root project
npm error     @openedx/frontend-plugin-framework@"^1.7.0" from @edx/[email protected]
npm error     node_modules/@edx/frontend-component-header
npm error       @edx/frontend-component-header@"^8.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-04-29T21_10_41_999Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-04-29T21_10_41_999Z-debug-0.log

@renovate renovate Bot force-pushed the renovate/react-error-boundary-6.x branch 3 times, most recently from 3e89d36 to 4d2dbdb Compare April 6, 2026 09:06
@renovate renovate Bot force-pushed the renovate/react-error-boundary-6.x branch 10 times, most recently from 034c098 to 5820bb7 Compare April 18, 2026 23:49
@renovate renovate Bot force-pushed the renovate/react-error-boundary-6.x branch 13 times, most recently from 4a6b831 to 49e94e5 Compare April 24, 2026 23:03
@renovate renovate Bot force-pushed the renovate/react-error-boundary-6.x branch 3 times, most recently from 7970c4d to 35f931f Compare April 28, 2026 15:56
@renovate renovate Bot force-pushed the renovate/react-error-boundary-6.x branch from 35f931f to 475cf98 Compare April 29, 2026 21:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants